Home > Use Cases > Taking an Offsite Copy

Taking an Offsite Copy

A sample SessionToken will be used throughout this use case.
The sample SessionToken will be: e65aedeb-a0e7-440c-8309-1cc0bcd920db

To start an offsite copy, the AltaroVirtualMachineRef is required. This way, the API can be instructed which configured VM to perform the offsite copy on. The following POST method starts an offsite copy operation on the VM. The response will contain a Success value, which states whether Altaro VM Backup managed to start the backup operation. When this is false, it means that something went wrong while the API was processing the request, but before sending it over to the Altaro Agent. When this occurs, it is generally due to an incorrect parameter, such as sending an AltaroVirtualMachineRef which does not exist. When the Success value is set to true, it does not mean that the operation is successful; it simply means that the operation could be processed by the API and could be successfully sent over to the Altaro Agent.

http://localhost:35113/api/instructions/take-offsitecopy/e65aedeb-a0e7-440c-8309-1cc0bcd920db/ba2e9cdc-0d85-48e6-8db7-a45c5a40819e

 

To monitor the activity and results of the operation, refer to the Take Backup operation above.

 

Note: A full list of available API commands can be found here